Poppy 2.0, not "v2"
Version notation is for engineers; people hear a generation. "2.0" signals a leap forward in plain language.
Recommendation
Public / marketing name: "Poppy 2.0." Keep v2 internally (board, pure_versions, this workstream). 2.0 is the launch story; v2 is the engineering tag. Never mix them in customer-facing copy.
| Context | Use |
|---|---|
| Marketing, UI, announcements, training | Poppy 2.0 (then just "Poppy" once launched) |
| Engineering, board, version ledger, deploys | v2 / pure_versions |
| After full rollout | "Poppy" — 2.0 fades; the name carries it |
A differentiated color scheme
Same PURE DNA — navy trust, gold warmth — with one new signature so 2.0 is unmistakable: Poppy Bloom, a refined coral drawn from the poppy flower itself. Used as an accent, never a flood.
Classic PURE chrome. Calm, established.
Bloom accent marks the new generation — active states, badges, CTAs.
What we say
One line
"Poppy 2.0 — the assistant that runs PURE. She knows your deals, acts for you safely, and gets sharper every day."
Built on the live tagline already in canon: "Poppy — the assistant that runs PURE."
What to repeat everywhere
- Knows your world — grounded in live MLS, your deals, PURE canon
- Acts, safely — does real work behind a one-tap approval
- Gets better — best model per task, learns your workspace
Tagline options
Launch plan & best practices
Sequence the reveal
- Teaser: "Something new is blooming" + 2.0 badge
- Live demo on acquisto.biz with the new thinking-state
- In-app announcement + changelog (what's new, in plain words)
- Email + SMS to members via Pure Send (personas-routed)
- Short training + an AI Roleplay "meet Poppy 2.0" scenario
- Feedback loop: a one-tap "How'd Poppy do?" after tasks
What works (and stays on-brand)
- Sell outcomes, not the model — "files your ticket," not "uses Claude"
- Show, don't tell — live demo > feature list
- Name the trust story up front: gated actions, audit, Fair Housing
- Lead with one hero capability, not ten
- Consistent lockup + signature color = instant recognition
- Set honest expectations; let users see what she's doing (transparency)
- Make adoption frictionless — meet users where they already are